Lcs sdxi data plane configuration system

ABSTRACT

A Logically Composed System (LCS) Smart Data Accelerator Interface (SDXI) data plane configuration system includes a resource management system coupled to an orchestrator device that is coupled to a plurality of resource devices. The resource management system discovers a first SDXI node in the plurality of resource devices, with the first SDXI node configured to process SDXI information and including a first memory subsystem that is configured to provide an SDXI memory space. The resource management system also identifies first memory system capabilit(ies) of the first memory subsystem included in the first SDXI node and, when the resource management system subsequently receives an LCS request, it composes an LCS that includes an SDXI data plane provided by the first SDXI node based on capabilities requirement(s) identified in the LCS request being satisfied by the first memory subsystem capabilit(ies) of the first memory subsystem included in the first SDXI node.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to configuring a Smart Data AcceleratorInterface (SDXI) data plane for an LCS that is provided using aninformation handling system.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

While conventional information handling systems such as, for example,server devices and/or other computing devices known in the art havetraditionally been provided with particular information handling systemscomponents that configure it to satisfy one or more use cases, newcomputing paradigms provide for the allocation of resources frominformation handling systems and/or information handling systemcomponents for use in Logically Composed Systems (LCSs) that may becomposed as needed to satisfy any computing intent/workload, and thendecomposed such that those resources may be utilized in other LCSs. Assuch, users of the LCSs may be provided with LCSs that meet theircurrent needs for any particular workload they require.

For example, LCSs are often provided using Bare Metal Server (BMS)systems or other resource systems known in the art, with resourcedevices included within and/or outside of those resource systems (e.g.,processing devices and memory devices on a motherboard in the BMS systemused to provide an Operating System (OS) for the LCS, storage devices,networking devices, etc.) used to perform the functionality for theLCSs, and often dynamically changing over the time period in which theLCS is provided. Furthermore, orchestrator devices in the BMS systemsmay orchestrate the provisioning of those LCSs while also includingresource devices that may be utilized to provide the functionality ofthose LCSs. To provide a specific example, an orchestrator device mayutilize memory systems provided by any of the resource devices discussedabove to provide for the storage and use of data by the LCS.

The Storage Networking Industry Association (SNIA) is developing theSmart Data Accelerator Interface (SDXI) in an effort to standardize adata plane for memory-to-memory data transfers/transforms (e.g., a dataplane that enables work submission and work completion involvingmemory-to-memory data transfers/transforms). For example, the SDXI maybe utilized to transfer data between memory addresses in memory addressspace in the same memory system (e.g., between two virtual machines, ortwo applications in the same virtual machine, that share the memoryaddress space in the same memory system). However, that standardizationhas not considered a control plane that would provide for theconfiguration of the memory address space that includes the memoryaddresses between which data will be transferred/transformed. As will beappreciated by one of skill in the art, the SDXI-based memory-to-memorydata transfers/transforms discussed above are relatively simple in astatic memory system including the memory address space having thememory addresses between which data will be moved and/or transformed.However, no SDXI control plane standardization exists that addresses howto configure memory system(s) included in a composed LCS to provide amemory address space so that the SDXI-based memory-to-memory datatransfers/transforms discussed above may be performed between memoryaddresses in that memory address space.

Accordingly, it would be desirable to provide an LCS SDXI data planeconfiguration system that addresses the issues discussed above.

SUMMARY

According to one embodiment, an Information Handling System (IHS)includes a processing system; and a memory system that is coupled to theprocessing system and that includes instructions that, when executed bythe processing system, cause the processing system to provide a SmartData Accelerator Interface (SDXI) control plane manager engine that isconfigured to: discover, in a plurality of resource devices that arecoupled to an orchestrator device, a first SDXI node, wherein the firstSDXI node is configured to process SDXI information and includes a firstmemory subsystem that is configured to provide an SDXI memory space;identify at least one first memory subsystem capability of the firstmemory subsystem included in the first SDXI node; receive, following thediscovery of the first SDXI node and the identification of the at leastone first memory subsystem capability of the first memory subsystemincluded in the first SDXI node, a Logically Composed System (LCS)request; and compose, based on at least one capabilities requirementidentified in the LCS request being satisfied by the at least one firstmemory subsystem capability of the first memory subsystem included inthe first SDXI node, an LCS that includes an SDXI data plane provided bythe first SDXI node.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an InformationHandling System (IHS).

FIG. 2 is a schematic view illustrating an embodiment of an LCSprovisioning system.

FIG. 3 is a schematic view illustrating an embodiment of an LCSprovisioning subsystem that may be included in the LCS provisioningsystem of FIG. 2 .

FIG. 4 is a schematic view illustrating an embodiment of a resourcesystem that may be included in the LCS provisioning subsystem of FIG. 3.

FIG. 5 is a schematic view illustrating an embodiment of theprovisioning of an LCS using the LCS provisioning system of FIG. 2 .

FIG. 6 is a schematic view illustrating an embodiment of theprovisioning of an LCS using the LCS provisioning system of FIG. 2 .

FIG. 7 is a schematic view illustrating an embodiment of an LCS SDXIdata plane configuration system provided according to the teachings ofthe present disclosure.

FIG. 8 is a flow chart illustrating an embodiment of a method forconfiguring an SDXI data plane for an LCS.

FIG. 9A is a schematic view illustrating an embodiment of the LCS SDXIdata plane configuration system of FIG. 7 operating during the method ofFIG. 8 .

FIG. 9B is a schematic view illustrating an embodiment of the LCS SDXIdata plane configuration system of FIG. 7 operating during the method ofFIG. 8 .

FIG. 9C is a schematic view illustrating an embodiment of the LCS SDXIdata plane configuration system of FIG. 7 operating during the method ofFIG. 8 .

FIG. 9D is a schematic view illustrating an embodiment of the LCS SDXIdata plane configuration system of FIG. 7 operating during the method ofFIG. 8 .

FIG. 9E is a schematic view illustrating an embodiment of the LCS SDXIdata plane configuration system of FIG. 7 operating during the method ofFIG. 8 .

FIG. 9F is a schematic view illustrating an embodiment of the LCS SDXIdata plane configuration system of FIG. 7 operating during the method ofFIG. 8 .

FIG. 10 is a schematic view illustrating an embodiment of an LCS thatmay be provided during the method of FIG. 8 .

FIG. 11 is a schematic view illustrating an embodiment of an LCS thatmay be provided during the method of FIG. 8 .

FIG. 12 is a schematic view illustrating an embodiment of an LCS thatmay be provided during the method of FIG. 8 .

DETAILED DESCRIPTION

For purposes of this disclosure, an information handling system mayinclude any instrumentality or aggregate of instrumentalities operableto compute, calculate, determine, classify, process, transmit, receive,retrieve, originate, switch, store, display, communicate, manifest,detect, record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, or otherpurposes. For example, an information handling system may be a personalcomputer (e.g., desktop or laptop), tablet computer, mobile device(e.g., personal digital assistant (PDA) or smart phone), server (e.g.,blade server or rack server), a network storage device, or any othersuitable device and may vary in size, shape, performance, functionality,and price. The information handling system may include random accessmemory (RAM), one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, ROM, and/orother types of nonvolatile memory. Additional components of theinformation handling system may include one or more disk drives, one ormore network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

In one embodiment, IHS 100, FIG. 1 , includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety of other mass storagedevices known in the art. IHS 100 further includes a display 110, whichis coupled to processor 102 by a video controller 112. A system memory114 is coupled to processor 102 to provide the processor with faststorage to facilitate execution of computer programs by processor 102.Examples of system memory may include random access memory (RAM) devicessuch as dynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

As discussed in further detail below, the Logically Composed System(LCS) Smart Data Accelerator Interface (SDXI) data plane configurationsystems and methods of the present disclosure may be utilized with LCSs,which one of skill in the art in possession of the present disclosurewill recognize may be provided to users as part of an intent-based,as-a-Service delivery platform that enables multi-cloud computing whilekeeping the corresponding infrastructure that is utilized to do so“invisible” to the user in order to, for example, simplify theuser/workload performance experience. As such, the LCSs discussed hereinenable relatively rapid utilization of technology from a relativelybroader resource pool, optimize the allocation of resources to workloadsto provide improved scalability and efficiency, enable seamlessintroduction of new technologies and value-add services, and/or providea variety of other benefits that would be apparent to one of skill inthe art in possession of the present disclosure.

With reference to FIG. 2 , an embodiment of a LCS provisioning system200 is illustrated that may be utilized with the LCS SDXI data planeconfiguration systems and methods of the present disclosure. In theillustrated embodiment, the LCS provisioning system 200 includes one ormore client devices 202. In an embodiment, any or all of the clientdevices may be provided by the IHS 100 discussed above with reference toFIG. 1 and/or may include some or all of the components of the IHS 100,and in specific examples may be provided by desktop computing devices,laptop/notebook computing devices, tablet computing devices, mobilephones, and/or any other computing device known in the art. However,while illustrated and discussed as being provided by specific computingdevices, one of skill in the art in possession of the present disclosurewill recognize that the functionality of the client device(s) 202discussed below may be provided by other computing devices that areconfigured to operate similarly as the client device(s) 202 discussedbelow, and that one of skill in the art in possession of the presentdisclosure would recognize as utilizing the LCSs described herein. Asillustrated, the client device(s) 202 may be coupled to a network 204that may be provided by a Local Area Network (LAN), the Internet,combinations thereof, and/or any of network that would be apparent toone of skill in the art in possession of the present disclosure.

As also illustrated in FIG. 2 , a plurality of LCS provisioningsubsystems 206 a, 206 b, and up to 206 c are coupled to the network 204such that any or all of those LCS provisioning subsystems 206 a-206 cmay provide LCSs to the client device(s) 202 as discussed in furtherdetail below. In an embodiment, any or all of the LCS provisioningsubsystems 206 a-206 c may include one or more of the IHS 100 discussedabove with reference to FIG. 1 and/or may include some or all of thecomponents of the IHS 100. For example, in some of the specific examplesprovided below, each of the LCS provisioning subsystems 206 a-206 c maybe provided by a respective datacenter or other computingdevice/computing component location (e.g., a respective one of the“clouds” that enables the “multi-cloud” computing discussed above) inwhich the components of that LCS provisioning subsystem are included.However, while a specific configuration of the LCS provisioning system200 (e.g., including multiple LCS provisioning subsystems 206 a-206 c)is illustrated and described, one of skill in the art in possession ofthe present disclosure will recognize that other configurations of theLCS provisioning system 200 (e.g., a single LCS provisioning subsystem,LCS provisioning subsystems that span multiple datacenters/computingdevice/computing component locations, etc.) will fall within the scopeof the present disclosure as well.

With reference to FIG. 3 , an embodiment of an LCS provisioningsubsystem 300 is illustrated that may provide any of the LCSprovisioning subsystems 206 a-206 c discussed above with reference toFIG. 2 . As such, the LCS provisioning subsystem 300 may include one ormore of the IHS 100 discussed above with reference to FIG. 1 and/or mayinclude some or all of the components of the IHS 100, and in thespecific examples provided below may be provided by a datacenter orother computing device/computing component location in which thecomponents of the LCS provisioning subsystem 300 are included. However,while a specific configuration of the LCS provisioning subsystem 300 isillustrated and described, one of skill in the art in possession of thepresent disclosure will recognize that other configurations of the LCSprovisioning subsystem 300 will fall within the scope of the presentdisclosure as well.

In the illustrated embodiment, the LCS provisioning subsystem 300 isprovided in a datacenter 302, and includes a resource management system304 coupled to a plurality of resource systems 306 a, 306 b, and up to306 c. In an embodiment, any of the resource management system 304 andthe resource systems 306 a-306 c may be provided by the IHS 100discussed above with reference to FIG. 1 and/or may include some or allof the components of the IHS 100. In the specific embodiments providedbelow, each of the resource management system 304 and the resourcesystems 306 a-306 c may include an orchestrator device. In someembodiments, the orchestrator device may be provided by the SystemControl Processor (SCP) device or Data Processing Unit (DPU) devicediscussed below, and may be conceptualized as an “enhanced” SmartNICdevice that may be configured to perform functionality that is notavailable in conventional SmartNIC devices such as, for example, theresource management functionality, LCS provisioning functionality,and/or other SCP/DPU functionality described herein. However, whiledescribed as being provided by an SCP device or DPU device, one of skillin the art in possession of the present disclosure will appreciate howthe orchestrator device of the present disclosure may also be providedby other devices that have been configured to perform the orchestratorfunctionality described below while remaining within the scope of thepresent disclosure as well.

In an embodiment, any of the resource systems 306 a-306 c may includeany of the resources described below coupled to an SCP device or DPUdevice that is configured to facilitate management of those resources bythe resource management system 304. Furthermore, the SCP device or DPUdevice included in the resource management system 304 may provide an SCPManager (SCPM) subsystem or DPU Manager (DPUM) subsystem that isconfigured to manage the SCP devices or DPU devices in the resourcesystems 306 a-306 c, and that performs the functionality of the resourcemanagement system 304 described below. In some examples, the resourcemanagement system 304 may be provided by a “stand-alone” system (e.g.,that is provided in a separate chassis from each of the resource systems306 a-306 c), and the SCPM subsystem or DPUM subsystem discussed belowmay be provided by a dedicated SCP device, DPU device, processing/memoryresources, and/or other components in that resource management system304. However, in other embodiments, the resource management system 304may be provided by one of the resource systems 306 a-306 c (e.g., it maybe provided in a chassis of one of the resource systems 306 a-306 c),and the SCPM subsystem or DPUM subsystem may be provided by an SCPdevice, DPU device, processing/memory resources, and/or any other anyother components in that resource system.

As such, the resource management system 304 is illustrated with dashedlines in FIG. 3 to indicate that it may be a stand-alone system in someembodiments, or may be provided by one of the resource systems 306 a-306c in other embodiments. Furthermore, one of skill in the art inpossession of the present disclosure will appreciate how SCP devices orDPU devices in the resource systems 306 a-306 c may operate to “elect”or otherwise select one or more of those SCP devices or DPU devices tooperate as the SCPM subsystem or DPUM subsystem that provides theresource management system 304 described below. However, while aspecific configuration of the LCS provisioning subsystem 300 isillustrated and described, one of skill in the art in possession of thepresent disclosure will recognize that other configurations of the LCSprovisioning subsystem 300 will fall within the scope of the presentdisclosure as well.

With reference to FIG. 4 , an embodiment of a resource system 400 isillustrated that may provide any or all of the resource systems 306a-306 c discussed above with reference to FIG. 3 . In an embodiment, theresource system 400 may be provided by the IHS 100 discussed above withreference to FIG. 1 and/or may include some or all of the components ofthe IHS 100. In the illustrated embodiment, the resource system 400includes a chassis 402 that houses the components of the resource system400, only some of which are illustrated and discussed below. In theillustrated embodiment, the chassis 402 houses an SCP device 406, butone of skill in the art in possession of the present disclosure willappreciate how the SCP device 406 may be replaced by the DPU devicedescribed herein while remaining within the scope of the presentdisclosure, with that DPU device provided by BLUEFIELD® DPU devicesavailable from NVIDIA® Corporation of Santa Clara, California, UnitedStates, DPU devices available from FUNGIBLE® Inc. of Santa Clara,California, United States, and/or other DPU devices known in the art.

In an embodiment, the SCP device 406 may include a processing system(not illustrated, but which may include the processor 102 discussedabove with reference to FIG. 1 ) and a memory system (not illustrated,but which may include the memory 114 discussed above with reference toFIG. 1 ) that is coupled to the processing system and that includesinstructions that, when executed by the processing system, cause theprocessing system to provide an SCP engine that is configured to performthe functionality of the SCP engines and/or SCP devices discussed below.Furthermore, the SCP device 406 may also include any of a variety of SCPcomponents (e.g., hardware/software) that are configured to enable anyof the SCP functionality described below.

In the illustrated embodiment, the chassis 402 also houses a pluralityof resource devices 404 a, 404 b, and up to 404 c, each of which iscoupled to the SCP device 406. For example, the resource devices 404a-404 c may include processing systems (e.g., first type processingsystems such as those available from INTEL® Corporation of Santa Clara,California, United States, second type processing systems such as thoseavailable from ADVANCED MICRO DEVICES (AMD)® Inc. of Santa Clara,California, United States, Advanced Reduced Instruction Set Computer(RISC) Machine (ARM) devices, Graphics Processing Unit (GPU) devices,Tensor Processing Unit (TPU) devices, Field Programmable Gate Array(FPGA) devices, accelerator devices, etc.); memory systems (e.g.,Persistence MEMory (PMEM) devices (e.g., solid state byte-addressablememory devices that reside on a memory bus), etc.); storage devices(e.g., Non-Volatile Memory express over Fabric (NVMe-oF) storagedevices, Just a Bunch Of Flash (JBOF) devices, etc.); networking devices(e.g., Network Interface Controller (NIC) devices, etc.); and/or anyother devices that one of skill in the art in possession of the presentdisclosure would recognize as enabling the functionality described asbeing enabled by the resource devices 404 a-404 c discussed below. Assuch, the resource devices 404 a-404 c in the resource systems 306 a-306c/400 may be considered a “pool” of resources that are available to theresource management system 304 for use in composing LCSs.

To provide a specific example, the SCP devices described herein mayprovide a “trusted” orchestrator device that operates as a Root-of-Trust(RoT) for their corresponding resource devices/systems, to provide anintent management engine for managing the workload intents discussedbelow, to perform telemetry generation and/or reporting operations fortheir corresponding resource devices/systems, to perform identityoperations for their corresponding resource devices/systems, provide animage boot engine (e.g., an operating system image boot engine) for LCSscomposed using a processing system/memory system controlled by that SCPdevice, and/or perform any other operations that one of skill in the artin possession of the present disclosure would recognize as providing thefunctionality described below. For example, the SCP device 406 may be“trusted” because it provides a root-of-trust for its correspondingresource devices/systems, and thus may be configured with restrictedaccess to its hardware and/or software that has been validated and ismaintained within a closed-loop infrastructure. For example, the SCPdevice 704 may run cryptographically signed software validated via theroot-of-trust, with connectivity to both a BMS BMC and the SCPM devicediscussed above, and with all communications internal to the closed-loopinfrastructure secured to ensure their veracity.

To contrast, the DPU device described herein may provide an “untrusted”orchestrator device that may include similarhardware/software/capabilities as the SCP device 406, but a user of theSCP device 406 may not be able to access suchhardware/software/capabilities on the SCP device 406 unless it is partof/connected to an authorized network. As will be appreciated by one ofskill in the art in possession of the present disclosure, the DPU devicemay be “untrusted” due to it having not been manufactured by amanufacturer of the computing system 202 (e.g., it may be obtained bythe manufacturer of the computing system 202 from any of a variety ofvendors that are not controlled by the manufacturer of the computingsystem 202), it having not been secured based on a lack of control overthe DPU device 204 by a manufacturer of the computing system 202, and/orbased on other “untrusted” factors that would be apparent to one ofskill in the art in possession of the present disclosure. As will beappreciated by one of skill in the art in possession of the presentdisclosure, a DPU device software stack differs from a conventionalInput/Output (IO) card that uses firmware configured to providededicated I/O and management functions, as in addition to firmware, theDPU device software stack will include a DPU operating system and a userspace that is customizable to configure/program the DPU device topresent resource devices to an operating system in the computing system202 outside the control of the manufacturer of the computing system,which can render that DPU device “untrusted” in many scenarios.

As discussed below, the SCP devices and/or DPU devices described hereinmay include Software-Defined Storage (SDS) subsystems, inferencesubsystems, data protection subsystems, Software-Defined Networking(SDN) subsystems, trust subsystems, data management subsystems,compression subsystems, encryption subsystems, and/or any otherhardware/software described herein that may be allocated to an LCS thatis composed using the resource devices/systems controlled by that SCPdevice. However, while an SCP device is illustrated and described asperforming the functionality discussed below, one of skill in the art inpossession of the present disclosure will appreciated that functionalitydescribed herein may be enabled on the DPU devices discussed above, aswell as other devices with similar functionality, while remaining withinthe scope of the present disclosure as well.

Thus, the resource system 400 may include the chassis 402 including theSCP device 406 connected to any combinations of resource devices. Toprovide a specific embodiment, the resource system 400 may provide a“Bare Metal Server” that one of skill in the art in possession of thepresent disclosure will recognize may be a physical server system thatprovides dedicated server hosting to a single tenant, and thus mayinclude the chassis 402 housing a processing system and a memory system,the SCP device 406, as well as any other resource devices that would beapparent to one of skill in the art in possession of the presentdisclosure. However, in other specific embodiments, the resource system400 may include the chassis 402 housing the SCP device 406 coupled toparticular resource devices 404 a-404 c. For example, the chassis 402 ofthe resource system 400 may house a plurality of processing systems(i.e., the resource devices 404 a-404 c) coupled to the SCP device 406.In another example, the chassis 402 of the resource system 400 may housea plurality of memory systems (i.e., the resource devices 404 a-404 c)coupled to the SCP device 406. In another example, the chassis 402 ofthe resource system 400 may house a plurality of storage devices (i.e.,the resource devices 404 a-404 c) coupled to the SCP device 406. Inanother example, the chassis 402 of the resource system 400 may house aplurality of networking devices (i.e., the resource devices 404 a-404 c)coupled to the SCP device 406. However, one of skill in the art inpossession of the present disclosure will appreciate that the chassis402 of the resource system 400 housing a combination of any of theresource devices discussed above will fall within the scope of thepresent disclosure as well.

As discussed in further detail below, the SCP device 406 in the resourcesystem 400 will operate with the resource management system 304 (e.g.,an SCPM subsystem) to allocate any of its resources devices 404 a-404 cfor use in a providing an LCS. Furthermore, the SCP device 406 in theresource system 400 may also operate to allocate SCP hardware and/orperform functionality, which may not be available in a resource devicethat it has allocated for use in providing an LCS, in order to provideany of a variety of functionality for the LCS. For example, the SCPengine and/or other hardware/software in the SCP device 406 may beconfigured to perform encryption functionality, compressionfunctionality, and/or other storage functionality known in the art, andthus if that SCP device 406 allocates storage device(s) (which may beincluded in the resource devices it controls) for use in a providing anLCS, that SCP device 406 may also utilize its own SCP hardware and/orsoftware to perform that encryption functionality, compressionfunctionality, and/or other storage functionality as needed for the LCSas well. However, while particular SCP-enabled storage functionality isdescribed herein, one of skill in the art in possession of the presentdisclosure will appreciate how the SCP devices 406 described herein mayallocate SCP hardware and/or perform other enhanced functionality for anLCS provided via allocation of its resource devices 404 a-404 c whileremaining within the scope of the present disclosure as well.

With reference to FIG. 5 , an example of the provisioning of an LCS 500to one of the client device(s) 202 is illustrated. For example, the LCSprovisioning system 200 may allow a user of the client device 202 toexpress a “workload intent” that describes the general requirements of aworkload that user would like to perform (e.g., “I need an LCS with 10gigahertz (Ghz) of processing power and 8 gigabytes (GB) of memorycapacity for an application requiring 20 terabytes (TB) ofhigh-performance protected-object-storage for use with ahospital-compliant network”, or “I need an LCS for a machine-learningenvironment requiring Tensorflow processing with 3 TB s of AcceleratorPMEM memory capacity”). As will be appreciated by one of skill in theart in possession of the present disclosure, the workload intentdiscussed above may be provided to one of the LCS provisioningsubsystems 206 a-206 c, and may be satisfied using resource systems thatare included within that LCS provisioning subsystem, or satisfied usingresource systems that are included across the different LCS provisioningsubsystems 206 a-206 c.

As such, the resource management system 304 in the LCS provisioningsubsystem that received the workload intent may operate to compose theLCS 500 using resource devices 404 a-404 c in the resource systems 306a-306 c/400 in that LCS provisioning subsystem, and/or resource devices404 a-404 c in the resource systems 306 a-306 c/400 in any of the otherLCS provisioning subsystems. FIG. 5 illustrates the LCS 500 including aprocessing resource 502 allocated from one or more processing systemsprovided by one or more of the resource devices 404 a-404 c in one ormore of the resource systems 306 a-306 c/400 in one or more of the LCSprovisioning subsystems 206 a-206 c, a memory resource 504 allocatedfrom one or more memory systems provided by one or more of the resourcedevices 404 a-404 c in one or more of the resource systems 306 a-306c/400 in one or more of the LCS provisioning subsystems 206 a-206 c, anetworking resource 506 allocated from one or more networking devicesprovided by one or more of the resource devices 404 a-404 c in one ormore of the resource systems 306 a-306 c/400 in one or more of the LCSprovisioning subsystems 206 a-206 c, and/or a storage resource 508allocated from one or more storage devices provided by one or more ofthe resource devices 404 a-404 c in one or more of the resource systems306 a-306 c/400 in one or more of the LCS provisioning subsystems 206a-206 c.

Furthermore, as will be appreciated by one of skill in the art inpossession of the present disclosure, any of the processing resource502, memory resource 504, networking resource 506, and the storageresource 508 may be provided from a portion of a processing system(e.g., a core in a processor, a time-slice of processing cycles of aprocessor, etc.), a portion of a memory system (e.g., a subset of memorycapacity in a memory device), a portion of a storage device (e.g., asubset of storage capacity in a storage device), and/or a portion of anetworking device (e.g., a portion of the bandwidth of a networkingdevice). Further still, as discussed above, the SCP device(s) 406 in theresource systems 306 a-306 c/400 that allocate any of the resourcedevices 404 a-404 c that provide the processing resource 502, memoryresource 504, networking resource 506, and the storage resource 508 inthe LCS 500 may also allocate their SCP hardware and/or perform enhancedfunctionality (e.g., the enhanced storage functionality in the specificexamples provided above) for any of those resources that may otherwisenot be available in the processing system, memory system, storagedevice, or networking device allocated to provide those resources in theLCS 500.

With the LCS 500 composed using the processing resources 502, the memoryresources 504, the networking resources 506, and the storage resources508, the resource management system 304 may provide the client device202 resource communication information such as, for example, InternetProtocol (IP) addresses of each of the systems/devices that provide theresources that make up the LCS 500, in order to allow the client device202 to communicate with those systems/devices in order to utilize theresources that make up the LCS 500. As will be appreciated by one ofskill in the art in possession of the present disclosure, the resourcecommunication information may include any information that allows theclient device 202 to present the LCS 500 to a user in a manner thatmakes the LCS 500 appear the same as an integrated physical systemhaving the same resources as the LCS 500.

Thus, continuing with the specific example above in which the userprovided the workload intent defining an LCS with a 10 Ghz of processingpower and 8 GB of memory capacity for an application with 20 TB ofhigh-performance protected object storage for use with ahospital-compliant network, the processing resources 502 in the LCS 500may be configured to utilize 10 Ghz of processing power from processingsystems provided by resource device(s) in the resource system(s), thememory resources 504 in the LCS 500 may be configured to utilize 8 GB ofmemory capacity from memory systems provided by resource device(s) inthe resource system(s), the storage resources 508 in the LCS 500 may beconfigured to utilize 20 TB of storage capacity from high-performanceprotected-object-storage storage device(s) provided by resourcedevice(s) in the resource system(s), and the networking resources 506 inthe LCS 500 may be configured to utilize hospital-compliant networkingdevice(s) provided by resource device(s) in the resource system(s).

Similarly, continuing with the specific example above in which the userprovided the workload intent defining an LCS for a machine-learningenvironment for Tensorflow processing with 3 TB s of Accelerator PMEMmemory capacity, the processing resources 502 in the LCS 500 may beconfigured to utilize TPU processing systems provided by resourcedevice(s) in the resource system(s), and the memory resources 504 in theLCS 500 may be configured to utilize 3 TB of accelerator PMEM memorycapacity from processing systems/memory systems provided by resourcedevice(s) in the resource system(s), while any networking/storagefunctionality may be provided for the networking resources 506 andstorage resources 508, if needed.

With reference to FIG. 6 , another example of the provisioning of an LCS600 to one of the client device(s) 202 is illustrated. As will beappreciated by one of skill in the art in possession of the presentdisclosure, many of the LCSs provided by the LCS provisioning system 200will utilize a “compute” resource (e.g., provided by a processingresource such as an x86 processor, an AMD processor, an ARM processor,and/or other processing systems known in the art, along with a memorysystem that includes instructions that, when executed by the processingsystem, cause the processing system to perform any of a variety ofcompute operations known in the art), and in many situations thosecompute resources may be allocated from a Bare Metal Server (BMS) andpresented to a client device 202 user along with storage resources,networking resources, other processing resources (e.g., GPU resources),and/or any other resources that would be apparent to one of skill in theart in possession of the present disclosure.

As such, in the illustrated embodiment, the resource systems 306 a-306 cavailable to the resource management system 304 include a Bare MetalServer (BMS) 602 having a Central Processing Unit (CPU) device 602 a anda memory system 602 b, a BMS 604 having a CPU device 604 a and a memorysystem 604 b, and up to a BMS 606 having a CPU device 606 a and a memorysystem 606 b. Furthermore, one or more of the resource systems 306 a-306c includes resource devices 404 a-404 c provided by a storage device610, a storage device 612, and up to a storage device 614. Furtherstill, one or more of the resource systems 306 a-306 c includes resourcedevices 404 a-404 c provided by a Graphics Processing Unit (GPU) device616, a GPU device 618, and up to a GPU device 620.

FIG. 6 illustrates how the resource management system 304 may composethe LCS 600 using the BMS 604 to provide the LCS 600 with CPU resources600 a that utilize the CPU device 604 a in the BMS 604, and memoryresources 600 b that utilize the memory system 604 b in the BMS 604.Furthermore, the resource management system 304 may compose the LCS 600using the storage device 614 to provide the LCS 600 with storageresources 600 d, and using the GPU device 318 to provide the LCS 600with GPU resources 600 c. As illustrated in the specific example in FIG.6 , the CPU device 604 a and the memory system 604 b in the BMS 604 maybe configured to provide an operating system 600 e that is presented tothe client device 202 as being provided by the CPU resources 600 a andthe memory resources 600 b in the LCS 600, with operating system 600 eutilizing the GPU device 618 to provide the GPU resources 600 c in theLCS 600, and utilizing the storage device 614 to provide the storageresources 600 d in the LCS 600. The user of the client device 202 maythen provide any application(s) on the operating system 600 e providedby the CPU resources 600 a/CPU device 604 a and the memory resources 600b/memory system 604 b in the LCS 600/BMS 604, with the application(s)operating using the CPU resources 600 a/CPU device 604 a, the memoryresources 600 b/memory system 604 b, the GPU resources 600 c/GPU device618, and the storage resources 600 d/storage device 614.

Furthermore, as discussed above, the SCP device(s) 406 in the resourcesystems 306 a-306 c/400 that allocates any of the CPU device 604 a andmemory system 604 b in the BMS 604 that provide the CPU resource 600 aand memory resource 600 b, the GPU device 618 that provides the GPUresource 600 c, and the storage device 614 that provides storageresource 600 d, may also allocate SCP hardware and/or perform enhancedfunctionality (e.g., the enhanced storage functionality in the specificexamples provided above) for any of those resources that may otherwisenot be available in the CPU device 604 a, memory system 604 b, storagedevice 614, or GPU device 618 allocated to provide those resources inthe LCS 500.

However, while simplified examples are described above, one of skill inthe art in possession of the present disclosure will appreciate howmultiple devices/systems (e.g., multiple CPUs, memory systems, storagedevices, and/or GPU devices) may be utilized to provide an LCS.Furthermore, any of the resources utilized to provide an LCS (e.g., theCPU resources, memory resources, storage resources, and/or GPU resourcesdiscussed above) need not be restricted to the same device/system, andinstead may be provided by different devices/systems over time (e.g.,the GPU resources 600 c may be provided by the GPU device 618 during afirst time period, by the GPU device 616 during a second time period,and so on) while remaining within the scope of the present disclosure aswell. Further still, while the discussions above imply the allocation ofphysical hardware to provide LCSs, one of skill in the art in possessionof the present disclosure will recognize that the LCSs described hereinmay be composed similarly as discussed herein from virtual resources.For example, the resource management system 304 may be configured toallocate a portion of a logical volume provided in a Redundant Array ofIndependent Disk (RAID) system to an LCS, allocate a portion/time-sliceof GPU processing performed by a GPU device to an LCS, and/or performany other virtual resource allocation that would be apparent to one ofskill in the art in possession of the present disclosure in order tocompose an LCS.

Similarly as discussed above, with the LCS 600 composed using the CPUresources 600 a, the memory resources 600 b, the GPU resources 600 c,and the storage resources 600 d, the resource management system 304 mayprovide the client device 202 resource communication information suchas, for example, Internet Protocol (IP) addresses of each of thesystems/devices that provide the resources that make up the LCS 600, inorder to allow the client device 202 to communicate with thosesystems/devices in order to utilize the resources that make up the LCS600. As will be appreciated by one of skill in the art in possession ofthe present disclosure, the resource communication information allowsthe client device 202 to present the LCS 600 to a user in a manner thatmakes the LCS 600 appear the same as an integrated physical systemhaving the same resources as the LCS 600.

As will be appreciated by one of skill in the art in possession of thepresent disclosure, the LCS provisioning system 200 discussed abovesolves issues present in conventional Information Technology (IT)infrastructure systems that utilize “purpose-built” devices (serverdevices, storage devices, etc.) in the performance of workloads and thatoften result in resources in those devices being underutilized. This isaccomplished, at least in part, by having the resource managementsystem(s) 304 “build” LCSs that satisfy the needs of workloads when theyare deployed. As such, a user of a workload need simply define the needsof that workload via a “manifest” expressing the workload intent of theworkload, and resource management system 304 may then compose an LCS byallocating resources that define that LCS and that satisfy therequirements expressed in its workload intent, and present that LCS tothe user such that the user interacts with those resources in samemanner as they would physical system at their location having those sameresources.

Referring now to FIG. 7 , an embodiment of an LCS SDXI data planeconfiguration system 700 is illustrated that may be provided accordingto the teachings of the present disclosure. In the illustratedembodiment, the LCS SDXI data plane configuration system 700 includes aresource system 702 that may be provided by any of the resource systems306 a, 306 b, 306 c, and 400, and/or the BMS systems 602, 604, and 606discussed above. The resource system 702 includes an orchestrator device704 that may be provided by the SCP devices, DPU devices, and/or otherorchestrator devices discussed above. The orchestrator device 704 mayinclude a processing system (not illustrated, but which may include theprocessor 102 discussed above with reference to FIG. 1 ) and a memorysystem (not illustrated, but which may include the memory 114 discussedabove with reference to FIG. 1 ) that is coupled to the processingsystem and that includes instructions that, when executed by theprocessing system, cause the processing system to provide anorchestrator engine 304 (e.g., the SCP engine, DPU engine, or otherorchestrator engines discussed above) that is configured to perform thefunctionality of the orchestrator engines and/or orchestrator devicesdiscussed below. In some of the specific examples provided below, theorchestrator engine 704 a may include a microvisor, hypervisor, and/orother sub-engine that is configured to assist in the provisioning theSDXI data plane discussed below, as well as provide any othermicrovisor/hypervisor functionality that would be apparent to one ofskill in the art in possession of the present disclosure.

In the illustrated embodiment, the orchestrator device 704 also includesone or more resource device(s) 704 b (e.g., resource device(s) 704 bthat are included on or directly connected to a circuit board thatprovides the orchestrator device 704), with the resource device(s) 704 bcoupled to the orchestrator engine 704 a (e.g., via a coupling betweenthe resource device(s) 704 b and the processing system). In the specificexamples discussed below, the resource device(s) 704 b may include atleast one SDXI node, which as discussed below may be provided by a“node” that is both configured to receive and process SDXI information(e.g., SDXI descriptors, SDXI functions, and/or other SDXI informationdefined by the SDXI specification), and includes a memory subsystem(e.g., one or more memory devices and/or portion(s) thereof, one or morestorage devices and/or portion(s) thereof, one or more GraphicsProcessing Unit (GPU) systems and/or portion(s) thereof, etc.) that isconfigured or otherwise capable of providing an SDXI memory space.

In the illustrated embodiment, the resource management system 702 alsoincludes one or more resource device(s) 706 (e.g., resource device(s)706 that are included in the chassis of a BMS system that may providethe resource system 702 as discussed above and that are not included onor connected to a circuit board that provides the orchestrator device704), with the resource device(s) 706 coupled to the orchestrator engine704 a (e.g., via a cabled coupling between the resource device(s) 706and the processing system). In the specific examples discussed below,the resource device(s) 706 may include at least one SDXI node, which asdiscussed below may be provided by a “node” that is both configured toreceive and process SDXI information (e.g., SDXI descriptors, SDXIfunctions, and/or other SDXI information defined by the SDXIspecification), and includes a memory subsystem (e.g., one or morememory devices and/or portion(s) thereof, one or more storage devicesand/or portion(s) thereof, one or more Graphics Processing Unit (GPU)systems and/or portion(s) thereof, etc.) that is configured or otherwisecapable of providing an SDXI memory space.

In the illustrated embodiment, the LCS SDXI data plane configurationsystem 700 also includes one or more resource device(s) 708 (e.g.,resource device(s) 708 that are located outside of the chassis of a BMSsystem that may provide the resource system 702 as discussed above),with the resource device(s) 708 coupled to the orchestrator engine 704 a(e.g., via a network coupling between the resource device(s) 708 and theprocessing system). In the specific examples discussed below, theresource device(s) 708 may include at least one SDXI node, which asdiscussed below may be provided by a “node” that is both configured toreceive and process SDXI information (e.g., SDXI descriptors, SDXIfunctions, and/or other SDXI information defined by the SDXIspecification n), and includes a memory subsystem (e.g., one or morememory devices and/or portion(s) thereof, one or more storage devicesand/or portion(s) thereof, one or more Graphics Processing Unit (GPU)systems and/or portion(s) thereof, etc.) that is configured or otherwisecapable of providing an SDXI memory space.

In the illustrated embodiment, the LCS SDXI data plane configurationsystem 700 also includes a resource management system 710 that may beprovided by the resource management system 304 discussed above, and thusmay include the SCPM device, the DPUM device, and/or other resourcemanagement systems discussed above. As illustrated, the resourcemanagement system 710 may include a processing system (not illustrated,but which may include the processor 102 discussed above with referenceto FIG. 1 ) and a memory system (not illustrated, but which may includethe memory 114 discussed above with reference to FIG. 1 ) that iscoupled to the processing system and that includes instructions that,when executed by the processing system, cause the processing system toprovide an SDXI control plane manager engine 710 a that is configured toperform the functionality of the SDXI control plane manager enginesand/or resource management systems discussed below. In the illustratedembodiment, the SDXI control plane manager engine 710 a is coupled tothe orchestrator engine 704 a (e.g., via a coupling between therespective processing systems that provide the SDXI control planemanager engine 710 a and the orchestrator engine 704 a).

In the illustrated embodiment, the LCS SDXI data plane configurationsystem 700 also includes a client device 712 that may be provided by anyof the client device(s) 202 discussed above, and thus may be provided bydesktop computing devices, laptop/notebook computing devices, tabletcomputing devices, mobile phones, and/or other computing devices thatwould be apparent to one of skill in the art in possession of thepresent disclosure. As discussed above, the client device 712 may becoupled to each of the resource management system 710 and theorchestrator device 704 in the resource system 702 (e.g., via anetwork). However, while a specific LCS SDXI data plane configurationsystem 700 has been illustrated and described, one of skill in the artin possession of the present disclosure will recognize that the LCS SDXIdata plane configuration system of the present disclosure may include avariety of components and/or component configurations for providingconventional LCS provisioning functionality, as well as thefunctionality discussed below, while remaining within the scope of thepresent disclosure as well.

Referring now to FIG. 8 , an embodiment of a method 800 configuring aSmart Data Accelerator Interface (SDXI) data plane for a LogicallyComposed System (LCS) is illustrated. As discussed below, the systemsand methods of the present disclosure provide for the configuration ofan SDXI data plane for an LCS using SDXI node(s) that are included inthe resource device(s) that provide that LCS. For example, the LCS SDXIdata plane configuration system of the present disclosure may include aresource management system coupled to an orchestrator device that iscoupled to a plurality of resource devices. The resource managementsystem discovers a first SDXI node in the plurality of resource devices,with the first SDXI node configured to process SDXI information andincluding a first memory subsystem that is configured to provide an SDXImemory space. The resource management system also identifies firstmemory system capabilit(ies) of the first memory subsystem included inthe first SDXI node and, when the resource management systemsubsequently receives an LCS request, it composes an LCS that includesan SDXI data plane provided by the first SDXI node based on capabilitiesrequirement(s) identified in the LCS request being satisfied by thefirst memory subsystem capabilit(ies) of the first memory subsystemincluded in the first SDXI node. As such, an LCS may be provided an SDXIdata plane made up of one or more memory subsystem, and in many casesmay be provided an SDXI data plane made up of different memory systemsand/or different types of memory devices.

As discussed below, embodiments of the systems and methods of thepresent disclosure may include an SDXI control plane manager that isconfigured to manage an SDXI control plane and make memory addressspaces provided by memory subsystems available to an LCS (e.g., to anapplication memory space for the LCS) using non-SDXI means (e.g.,microvisors, hypervisors, and/or other configuration subsystems that maybe included in the orchestrator device that provides the LCS asdiscussed above). As discussed below, the SDXI control plane manager mayalso provide for the opaque scaling (e.g., from the perspective of theclient device/LCS) of memory resources as memory resource demands of theLCS (e.g., application(s) on the LCS) increase. As such, SDXI techniquesmay be leveraged by the SDXI control plane manager to abstractLCS/application memory resource access using, for example, heterogeneousaccelerators, different classes/tiers of memory subsystems, and/or othermemory components that would be apparent to one of skill in the art inpossession of the present disclosure.

As discussed below, the SDXI control plane manager of the presentdisclosure may operate to utilize any discovered SDXI-enabled resourcesto provide in an SDXI data plane for an LCS, and then apply variouslevels of abstraction of that SDXI data plane based on the SDXI accesscapabilities of that LCS. As such, the SDXI control plane manager maydetermine the configuration of the SDXI data plane for an LCS and howthat SDXI data plane is presented to that LCS, as well as how that LCSmay operate to access that SDXI data plane. As discussed below, the SDXIdata plane may then be provided for the LCS via an application addressspace, a virtual machine address space, a Java virtual machine addressspace, an address space provided via two or more SDXI nodes, and/or in avariety of other manners that would be apparent to one of skill in theart in possession of the present disclosure. Furthermore, the SDXI dataplane may then be assigned directly to an LCS, or may be assigned to theresource system (e.g., a BMS system) that hosts the LCS (i.e., thatincludes the processing system/memory system that provide the operatingsystem for that LCS) in order to allow that LCS to access the SDXI dataplane via an SDXI service that is configured to enable access to theSDXI data plane.

The method 800 begins at block 802 where a resource management systemdiscovers one or more SDXI node(s) in resource device(s) that arecoupled to an orchestrator device. In an embodiment, at block 802, theSDXI control plane manager engine 710 a in the resource managementsystem 710 may perform SDXI node discovery operations in order todiscover SDXI node(s) provided by any of the resource device(s) 704 bincluded on the orchestrator device 704, any of the resource device(s)706 included in the resource system 702 but not included on theorchestrator device 704, and/or any of the resource device(s) 708located outside of the resource system 702. For example, as illustratedin FIG. 9A, the resource device(s) 704 b, 706, and 708 and/or theorchestrator device 704 a that provide SDXI nodes may perform SDXI noderegistration operations 900 that include transmitting SDXI nodeidentification messages to the SDXI control plane manager engine 710 ain the resource management system 710 that cause the SDXI control planemanager engine 710 a to identify the SDXI nodes included in the resourcedevice(s) 704 b, 706, and 708 at block 802.

For example, any of the resource device(s) 704 b, 706, and 708 mayprovide an SDXI node that includes a memory subsystem (e.g., included inor with one or more memory devices, storage devices, Graphics ProcessingUnits (GPUs), etc.) that is configured or otherwise capable of providingan SDXI memory space, with that SDXI node also including a processingsystem and memory system that includes instruction that, when executedby the processing system, cause the processing system to provide an SDXInode engine that is configured to receive and process SDXI informationsuch as SDXI descriptors, SDXI functions, and/or other SDXI informationdefined by the SDXI specification. Furthermore, the SDXI node engine inany of the resource device(s) 704 b, 706, and 708 may also be configuredto register its SDXI node (which is provided by the SDXI node engine andthe SDXI memory-space-capable memory subsystem in a resource device asdiscussed above) with the SDXI control plane manager engine 710 a withvia the orchestrator device 704 a as illustrated in FIG. 9A, or directlyin embodiments in which that resource device includes a direct couplingwith the resource management system 710. As such, at block 802 the SDXIcontrol plane manager engine 710 a in the resource management system 710may discover SDXI nodes provided by any of the resource devices 704 a,706, and/or 708.

In another example, any of the resource device(s) 704 b, 706, and 708may include a memory subsystem (e.g., included in or with one or morememory devices, storage devices, Graphics Processing Units (GPUs), etc.)that is configured or otherwise capable of providing an SDXI memoryspace, while the orchestrator engine 704 a may be configured to performthe SDXI node engine operations discussed above for that resource devicethat include receiving and processing SDXI information such as SDXIdescriptors, SDXI functions, and/or other SDXI information defined bythe SDXI specification. Furthermore, the orchestrator engine 704 a mayalso be configured to perform the SDXI node engine operations discussedabove for that resource device that include registering its SDXI node(which is provided by the orchestrator engine 704 a and the SDXImemory-space-capable memory subsystem in a resource device as discussedabove) with the SDXI control plane manager engine 710 a as illustratedin FIG. 9A. Further still, while not illustrated or discussed in detailherein, one of skill in the art in possession of the present disclosurewill recognize how the SDXI nodes of the present disclosure may beconfigured to de-register with the SDXI control plane manager engine 710a in a manner similar to the registration discussed above.

As such, at block 802 the SDXI control plane manager engine 710 a in theresource management system 710 may discover SDXI nodes provided by acombination of the orchestrator engine 704 a in the orchestrator device704 and any of the resource devices 704 a, 706, and/or 708. Furthermore,while not illustrated or described in detail, one of skill in the art inpossession of the present disclosure will appreciate how an orchestratordevice in a resource system that includes any of the resource device(s)708 may operate to perform the SDXI node engine operations discussedabove that include receiving and processing the SDXI information andregistering an SDXI node that includes the SDXI memory-space-capablememory subsystem in any of the resource device(s) 708 while remainingwithin the scope of the present disclosure as well.

However, while a few specific examples of the registration/discovery ofSDXI nodes with/by the SDXI control plane manager engine 710 a/resourcemanagement system 710 have been described, one of skill in the art inpossession of the present disclosure will appreciate how SDXI nodes inthe LCS SDXI data plane configuration system of the present disclosuremay be discovered in other manners that will fall within the scope ofthe present disclosure as well. As such, following block 802, the SDXIcontrol plane manager engine 710 a in the resource management system 710may have discovered any SDXI nodes that include or are provided by theresource device(s) 704 b, 706, and/or 708 coupled to the orchestratordevice 704, and may store the identity of those SDXI nodes in a databasethat is accessible to the SDXI control plane manager engine 710 a and inassociation with the orchestrator device 704 in order to, for example,allow any LCSs that are subsequently composed for provisioning by theorchestrator device 704 to be provided an SDXI data plane using any ofthose SDXI nodes, as discussed in further detail below.

The method 800 then proceeds to block 804 where the resource managementsystem identifies memory subsystem capabilities of memory subsystem(s)included in the SDXI node(s). With reference to FIG. 9B, in anembodiment of block 804, the SDXI control plane manager engine 710 a inthe resource management system 710 may perform memory subsystemcapabilities identification operations 902 that include transmitting amemory subsystem capabilities reporting request to SDXI node(s) providedby any of the resource device(s) 704 b included on the orchestratordevice 704, any of the resource device(s) 706 included in the resourcesystem 702 but not included on the orchestrator device 704, and/or anyof the resource device(s) 708 located outside of the resource system702. With reference to FIG. 9C, in an embodiment of block 804 and inresponse to receiving the memory subsystem capabilities reportingrequest, the SDXI node(s) provided by any of the resource device(s) 704b included on the orchestrator device 704, any of the resource device(s)706 included in the resource system 702 but not included on theorchestrator device 704, and/or any of the resource device(s) 708located outside of the resource system 702, may perform memory subsystemcapabilities reporting operations 904 that include transmitting a memorysubsystem capabilities report to the SDXI control plane manager engine710 a in the resource management system 710. As such, at block 804 theSDXI control plane manager engine 710 a in the resource managementsystem 710 may identify the memory capabilities of the memory subsystemincluded in any SDXI node provided by any of the resource devices 704 a,706, and/or 708.

For example, as discussed above, an SDXI node may be provided by any ofthe resource device(s) 704 b, 706, and 708 (e.g., it may include amemory subsystem and an SDXI node engine provided by that resourcedevice) and, as illustrated in FIGS. 9B and 9C, the SDXI control planemanager engine 710 a in the resource management system 710 may transmitthe memory subsystem capabilities reporting request via the orchestratordevice 704 to the SDXI node engine included in any resource device, andreceive the memory subsystem capabilities report back from that SDXInode engine via the orchestrator device 704. However, in embodiments inwhich a resource device includes a direct coupling with the resourcemanagement system 710, the memory subsystem capabilities reportingrequest and the memory subsystem capabilities report may be exchangeddirectly between the SDXI control plane manager engine 710 a and theSDXI node engine in any resource device. As such, at block 804 the SDXIcontrol plane manager engine 710 a in the resource management system 710may identify the memory capabilities of the memory subsystem included inany SDXI node provided by any of the resource devices 704 a, 706, and/or708.

In another example, as discussed above, an SDXI node may be provided byany of the resource device(s) 704 b, 706, and 708 (e.g., it may includea memory subsystem provided by that resource device) and theorchestrator device 704 a (e.g., the orchestrator device 704 a mayperform the SDXI node engine operations discussed above). As such,similarly as illustrated in FIGS. 9B and 9C, the SDXI control planemanager engine 710 a in the resource management system 710 may transmitthe memory subsystem capabilities reporting request to the orchestratorengine 704 a in the orchestrator device 704, and may receive the memorysubsystem capabilities report back from the orchestrator engine 704 a inthe orchestrator device 704, and in some situations those operations maynot involve the resource device(s) 704 b, 706, and 708 (e.g., when theorchestrator engine 704 a has previously identified the memory subsystemcapabilities of the memory subsystems in those resource device(s) 704 b,706, and 708). As such, at block 804 the SDXI control plane managerengine 710 a in the resource management system 710 may identify thememory capabilities of the memory subsystem included in any SDXI nodeprovided by a combination of the orchestrator device 704 and any of theresource devices 704 a, 706, and/or 708. Furthermore, while notillustrated or described in detail, one of skill in the art inpossession of the present disclosure will appreciate how an orchestratordevice in a resource system that includes any of the resource device(s)708 may operate to receive the memory subsystem capabilities reportingrequest and provide the memory subsystem capabilities report whileremaining within the scope of the present disclosure as well.

In an embodiment, the memory subsystem capabilities report discussedabove may identify any of a variety of capabilities of the memorysubsystems included in any of the SDXI nodes discovered at block 802.For example, a memory subsystem capabilities report provided by an SDXInode engine or the orchestrator engine 704 a that provides an SDXI nodemay identify a type of memory device that provides that memorysubsystem, a size of that memory subsystem, connection details for thatmemory subsystem (e.g., to the orchestrator device), and/or any othermemory subsystem capabilities that would be apparent to one of skill inthe art in possession of the present disclosure. To provide a specificexample, a memory subsystem capabilities report may identify that amemory subsystem in an SDXI node is provided by a High Bandwidth Memory(HBM) memory device and HBM memory interface, with a memory subsystemsize of 2 GB. In another specific example, a memory subsystemcapabilities report may identify that a memory subsystem in an SDXI nodeis provided by a Persistent MEMory (PMEM) memory device and includes amemory subsystem size of 100 GB. In yet another specific example, amemory subsystem capabilities report may identify that a memorysubsystem in an SDXI node includes a memory subsystem size of 1 TB andis connected to the orchestrator device 704 by a 100 GbE networkconnection.

However, while several specific examples of memory subsystemcapabilities of memory subsystems in SDXI nodes have been described, oneof skill in the art in possession of the present disclosure willappreciate that any memory subsystem capabilities of SDXI nodes in theLCS SDXI data plane configuration system 700 of the present disclosuremay be identified at block 804 while remaining within the scope of thepresent disclosure as well. As such, following block 804, the SDXIcontrol plane manager engine 710 a in the resource management system 710may have identified the memory subsystem capabilities of any SDXI nodesthat include or are provided by the resource device(s) 704 b, 706,and/or 708 coupled to the orchestrator device 704, and may store thememory subsystem capabilities of those SDXI nodes in a database that isaccessible to the SDXI control plane manager engine 710 a and inassociation with those SDXI nodes and the orchestrator device 704 inorder to, for example, allow any LCSs that are subsequently composed forprovisioning by the orchestrator device 704 to be provided an SDXI dataplane using any of those SDXI nodes, as discussed in further detailbelow.

The method 800 then proceeds to decision block 806 where it isdetermined whether an LCS request has been received. In an embodiment,at decision block 806, the resource management system 710 may operate tomonitor whether an LCS request to compose an LCS has been received fromthe client device 712. As discussed above and in further detail below,client devices may provide workload intents to the resource managementsystem 710 in order to request the composition of an LCS for performinga workload, and one of skill in the art in possession of the presentdisclosure will appreciate how the resource management system 710 maymonitor for such a workload intent in a variety of manners that willfall within the scope of the present disclosure as well.

If, at decision block 806, it is determined that an LCS request has notbeen received, the method 800 returns to block 802. As such, the method800 may loop such that that the resource management system operates todiscover SDXI nodes in the resource device(s) 704 b, 706, and 708coupled to the orchestrator device 704, and identify the memorysubsystem capabilities of those SDXI nodes, as long as no LCS request asbeen received. As will be appreciated by one of skill in the art inpossession of the present disclosure, resource devices and SDXI nodesprovided by those resource devices may be disconnected from theorchestrator device 704 and/or connected to the orchestrator device 704over time, and thus the looping of the method 800 between blocks 802,804, and 806 (i.e., as long as no LCS request has been received) willcause the SDXI control plane manager engine 710 a in the resourcemanagement system 710 to dynamically and continuously update the SDXInodes coupled to the orchestrator device 704 in order to, for example,remove SDXI nodes from their association with the orchestrator device704 in its database during a second iteration of the method 800subsequent to their disconnection from the orchestrator device 704subsequent to their discovery during a first iteration of the method800, add SDXI nodes as being associated with the orchestrator device 704in its database during a second iteration of the method 800 that werenot discovered during the first iteration of the method and connected tothe orchestrator device 704 prior the second iteration of the method800, etc. As such, the availability of SDXI nodes for use in providing adata plane for LCSs that will be provided using the orchestrator device704 may update dynamically as those SDXI nodes are connected to anddisconnected from the orchestrator device 704.

If at decision block 806, it is determined that an LCS request has beenreceived, the method 800 proceeds to block 808 where the resourcemanagement system composes an LCS including an SDXI data plane providedby SDXI node(s) based on one or more capabilities requirement(s) in theLCS request being satisfied by memory subsystem capabilities of thememory subsystem(s) included in the SDXI node(s). In an embodiment, atdecision block 806, the client device 712 may perform LCS requestoperations 906 that may include transmitting an LCS request to theresource management system 710. As discussed above, the client device712 may provide the LCS request at decision block 806 as a “workloadintent” that describes the general requirements of a workload that auser of the client device 712 would like to perform, although othertechniques for requesting an LCS will fall within the scope of thepresent disclosure as well. As such, one of skill in the art inpossession of the present disclosure will appreciate how the LCSrequest/workload intent may allow for the identification of one or morecapability requirements (e.g., the processing requirements, memoryrequirements, storage requirements, networking requirements, etc. of anLCS as determined by the workload intent as discussed above) for therequested LCS that will enable it to perform the workload. However,while a specific LCS request has been described, one of skill in the artin possession of the present disclosure will appreciate that othertechniques for requesting an LCS will fall within the scope of thepresent disclosure as well.

As such, at decision block 806 the resource management system 710 maydetermine that an LCS request has been received from the client device712 and, in response, at block 808 the resource management system 710may operate to compose an LCS based on the resource device(s) 704 b,706, and/or 708 similarly as discussed above. In a specific example,based on the capability requirements identified in the workloadintent/LCS request, the resource management system 710 may identify aprocessing system and memory system included in the resource device(s)706 in the resource system 702 and compose the LCS such that thatprocessing system and memory system may be configured to provide anoperating system for the LCS. Furthermore, in this specific example, theresource management system 710 may identify a storage system andnetworking system included in the resource device(s) 706 in the resourcesystem 702 and/or the resource device(s) 708 outside the resource system702 for use by the operating system of the LCS. Further still, in thisspecific example, the resource management system 710 may identify theresource device(s) 704 b included on the orchestrator device 704 for useby the operating system of the LCS.

In addition, at block 808, the resource management system 710 mayidentify memory resources provided by one or more of the SDXI nodesdiscovered at block 802 for use by the operating system of the LCS. Forexample, using on the capability requirements identified from theworkload intent/LCS request, the resource management system 710 mayaccess its database that associates the SDXI nodes with their memorysubsystem capabilities in order to determine whether any of thecapability requirements of the LCS are satisfied by the memory subsystemcapabilities of the SDXI nodes. Thus, continuing with the specificmemory subsystem capabilities requirements provided in the examplesabove, the resource management system 710 may determine whether thecapabilities requirements for the LCS include particular memory types(e.g., HBM memory with HBM memory device(s) and HBM memory interface(s),PMEM memory with PMEM memory devices, etc.), particular memory sizes(e.g., 2 GB, 100 GB, 1 TB, etc.), particular memory network connectionbandwidths (e.g., a 100 GbE network connection to the memory), etc. Assuch, at block 808 the resource management system 710 may compose an LCSbased on the LCS request received at decision block 806 using any of theSDXI nodes discovered at block 802.

As such, at block 808, the resource management subsystem 710 may composethe LCS at block 808 using SDXI nodes backed by, provided by, orotherwise including memory subsystems in different memory systems (e.g.,a memory subsystem provided by a memory system in one of the resourcedevice(s) 706 and a memory subsystem provided by a memory system in oneof the resource device(s) 708), memory subsystems in memory devices ofdifferent memory types (a memory subsystem provided by a first type ofmemory device and a memory subsystem provided by a second type of memorydevice), and/or backed a variety of different memory subsystemcomponents and configurations that would be apparent to one of skill inthe art in possession of the present disclosure.

With reference to FIG. 9E, in response to composing the LCS, theresource management system 710 may perform LCS provisioning instructionoperations 908 that may include transmitting LCS provisioninginstructions to the orchestrator engine 704 a in the orchestrator device704. Furthermore, the LCS provisioning instruction operations 908 mayalso include the SDXI control plane manager engine 710 a providinginstructions, commands, and/or other information that is configured tomap the SDXI nodes that were used to compose the LCS and that areprovided by the resource device(s) 704 b, 706, and/or 708 (and in somecases, the orchestrator engine 704 a) to an SDXI data plane for the LCS.

With reference to FIG. 9F, in response to receiving the LCS provisioninginstructions, the orchestrator engine 704 a may perform LCS provisioningoperations 910 that include using the resource device(s) 704 b, 706, and708 to provide an LCS 912 to the client device 712 similarly asdiscussed above. Furthermore, the LCS provisioning operations 910include providing the LCS 912 including an SDXI data plane 914 providingone or more SDXI nodes 914 a, 914 b, and up to 914 c, any of which maybe provided by one of the resource device(s) 704 b, 706, and 708 (and insome cases the orchestrator engine 704 a as well), as discussed above.For example, the microvisor or hypervisor provided by the orchestratorengine 704 a may integrate with the SDXI control plane manager engine710 a and operate with other components of the orchestrator engine 704a/orchestrator device 704 to provide the LCS and the SDXI data planeusing the SDXI node(s) 914 a, 914 b, and/or 914 c. As such, one of skillin the art in possession of the present disclosure will recognize thatthe LCS (e.g., an application provided on the LCS) may utilize (e.g., atthe instruction of the client device 712) the SDXI node(s) 914 a, 914 b,and/or 914 c that provide the SDXI data plane 904 in order to performthe SDXI memory-to-memory data transfers/transforms discussed above, aswell as perform any other SDXI data plane operations that would beapparent to one of skill in the art in possession of the presentdisclosure.

As will be appreciated by one of skill in the art in possession of thepresent disclosure, each of the SDXI nodes 914 a-914 c may include aconfiguration interface that enables their management by the SDXIcontrol plane manager engine 710 a, and thus may each be configured toprovide an SDXI data resource target and responder in order to provide arespective resource target for the SDXI data plane 914. Furthermore, theLCS 912 may discover and utilize any resources presented to it by theorchestrator device 704 and backed by the resource device(s) 704 b, 706,and/or 708 (e.g., processing systems, memory systems, storage systems,networking systems, etc.), and one or more of those resources (e.g.,memory resources, storage resources, etc.) may be backed by any of theSDXI nodes 914 a-914 c and/or the SDXI data plane 814. As will beappreciated by one of skill in the art in possession of the presentdisclosure, the SDXI data plane 914/SDXI nodes 914 a-914 c may provide aconsistent access and programming model for the LCS 914 that isindependent of the resource devices that are backing the SDXI data plane914.

As such, one of skill in the art in possession of the present disclosurewill appreciate how the SDXI control plane manager engine 710 a mayoperate to provide the LCS 912 with the SDXI data plane 914 backed bySDXI-enabled resource devices, and may operate with the orchestratorengine 704 a (e.g., a microvisor, hypervisor, etc.) to allow the LCS 912to access those SDXI-enabled resource devices with varying levels ofabstraction depending on the SDXI access capabilities of the LCS 912. Assuch, the SDXI control plane manager engine 710 a and orchestratorengine 704 a may control how the SDXI data plane 914 is visible toand/or accessible to the LCS 912. Thus, as discussed below, the“envelope” of the SDXI data plane 914 may include application addressspace, virtual machine address space, Java Virtual Machine (JVM) addressspace, addresses spaces provided by two or more of the SDXI nodes, etc.Furthermore, in some embodiments, the LCS 912 may not have the SDXI dataplane 914 assigned directly to it, and that SDXI data plane 914 mayinstead be assigned to the resource system 702 hosting the LCS 912(e.g., a BMS system with the processing system and resource system thatprovide an operating system for the LCS 912), with the LCS 912 utilizingthe SDXI data plane 914 via a service (e.g., a file service) that hasbeen modified to utilize the SDXI data plane 914.

With reference to FIGS. 10, 11, and 12 , different embodiments of theLCS 912 are illustrated that may be provided based on how the SDXI dataplane 914 provided with the LCS 912 is abstracted by the SDXI controlplane manager engine 710 a and orchestrator engine 704 a, and one ofskill in the art in possession of the present disclosure will appreciatehow relatively tight integration of the SDXI control plane managerengine 710 a and the needs of the LCS 912 will allow the most feasibleabstraction interface between the LCS 912 and the SDXI data plane 914 tobe provided. For example, FIG. 10 illustrates an LCS 1000 that may beprovided by the orchestrator engine 704 a as the LCS 912 with the SDXIdata plane 914. As will be appreciated by one of skill in the art inpossession of the present disclosure, the LCS 1000 illustrated in FIG.10 is an example of an SDXI-memory-space-aware LCS that can “see” theSDXI memory space provided by the SDXI data plane 914 and that isconfigured to directly instruct the SDXI memory-to-memory datatransfers/transforms discussed above. As such, the LCS 1000 may includean SDXI-enabled application 1000 a, an SDXI library 1000 b, an SDXIdevice driver 1000 c, and an SDXI device function 1000 d, and one ofskill in the art in possession of the present disclosure will appreciatehow the SDXI-enabled application 1000 a may utilize the SDXI library1000 b, the SDXI device driver 1000 c, and the SDXI device function 1000d to provide SDXI memory-to-memory data transfer/transform instructions(e.g., using SDXI descriptors, SDXI functions, etc.) via theorchestrator engine 704 a to the SDXI-enabled resource devices in orderto cause SDXI memory-to-memory data transfers/transforms between memoryaddress space that is provided by the SDXI node(s) 914 a-914 c in theSDXI data plane 914 and that is included in memory subsystems providedby the resource device(s) 704 b, 706, and 708.

In another example, FIG. 11 illustrates an LCS 1100 that may be providedby the orchestrator engine 704 a as the LCS 912 with the SDXI data plane914. As will be appreciated by one of skill in the art in possession ofthe present disclosure, the LCS 1100 illustrated in FIG. 11 is anexample of a non-SDXI-memory-space-aware LCS that cannot “see” the SDXImemory space provided by the SDXI data plane 904 and that is not capableof directly instructing the SDXI memory-to-memory datatransfers/transforms discussed above. As such, the LCS 1100 may includea non-SDXI-enabled application 1100 a, while the orchestrator engine 704a includes an SDXI-enabled service 1102 a, an SDXI library 1102 b, anSDXI device driver 1102 c, and an SDXI device function 1102 d, and oneof skill in the art in possession of the present disclosure willappreciate how the SDXI-enabled service 1102 a may receive data transferinstructions from the non-SDXI application 1100 a and utilize the SDXIlibrary 1102 b, the SDXI device driver 1102 c, and the SDXI devicefunction 1102 d in order to provide SDXI memory-to-memory datatransfer/transform instructions (e.g., using SDXI descriptors, SDXIfunctions, etc.) to the SDXI-enabled resource devices that cause SDXImemory-to-memory data transfers/transforms between memory address spacethat is provided by the SDXI node(s) 914 a-914 c in the SDXI data plane914 and that is included in memory subsystems provided by the resourcedevice(s) 704 b, 706, and 708. As such, the non-SDXI application 1100 aand the LCS 1100 may instruct non-SDXI data transfers, and theorchestrator engine 704 a may cause SDXI memory-to-memory datatransfers/transforms to be performed in response and without theknowledge of the non-SDXI application 100 a and the LCS 1100.

In another example, FIG. 12 illustrates an LCS 1200 that may be providedby the orchestrator engine 704 a as the LCS 912 with the SDXI data plane914. As will be appreciated by one of skill in the art in possession ofthe present disclosure, the LCS 1200 illustrated in FIG. 12 is anexample of an LCS that has been modified to instruct the SDXImemory-to-memory data transfers/transforms discussed above for non-SDXIapplications that cannot “see” the SDXI memory space provided by theSDXI data plane 904 and that are not capable of instructing the SDXImemory-to-memory data transfers/transforms discussed above. As such, theLCS 1200 may include a non-SDXI-enabled application 1200 a, SDXI-enabledmiddleware 1200 b, and an SDXI library 1200 c, while the orchestratorengine 704 a may include an SDXI device driver 1202 c and an SDXI devicefunction 1202 d, and one of skill in the art in possession of thepresent disclosure will appreciate how the SDXI-enabled middleware 1200b may receive data transfer instructions from the non-SDXI application1200 a and utilize the SDXI library 1200 c in the LCS 1200, as well asthe SDXI device driver 1202 a and the SDXI device function 1202 b in theorchestrator engine 704 a, in order to provide SDXI memory-to-memorydata transfer/transform instructions (e.g., using SDXI descriptors, SDXIfunctions, etc.) to the SDXI enabled resource devices that cause SDXImemory-to-memory data transfers/transforms between memory address spacethat is provided by the SDXI node(s) 914 a-914 c in the SDXI data plane914 and that is included in memory subsystems provided by the resourcedevice(s) 704 b, 706, and 708. Furthermore, while illustrated anddescribed as being included in the orchestrator engine 704 a, the SDXIdevice driver 1202 c and an SDXI device function 1202 d may be includedin the LCS 1200 while remaining within the scope of the presentdisclosure as well.

As such, the non-SDXI application 1200 a may instruct non-SDXI datatransfers, and the SDXI-enabled middleware 1200 b may cause SDXImemory-to-memory data transfers/transforms to be performed without theknowledge of the non-SDXI application 1200 a and the LCS 1200. In aspecific example, the SDXI-enabled middleware 1200 b may utilize a GNU CLibrary (glibc), a Java Virtual Machine (JVM), or a Structured QueryLanguage (SQL) application to perform a memcopy on behalf of thenon-SDXI-enabled application 1200 a and between memory address spacethat is provided by the SDXI node(s) 914 a-914 c in the SDXI data plane914 and that is included in memory subsystems provided by the resourcedevice(s) 704 b, 706, and 708, with that memcopy initiated by thefollowing “Int sdxi_memcpy(dst, src,) command:

{  #ifdef SDXI_MEMCPY  {  Perform_dma(dst, src)  }  #else  {  Mov [mem],RAX  } }

While not discussed in detail herein, and similarly as discussed above,SDXI-enabled resource devices that provide (or are included in) the SDXInodes may be connected to and disconnected from the orchestrator device704, and thus the SDXI control plane manager engine 710 a and/or theorchestrator engine 704 a may operate to remove SDXI nodes from the SDXIdata plane 914 and/or add SDXI nodes to the SDXI data plane 914 duringthe provisioning of the LCS 912, thus providing an SDXI data plane thatis dynamically backed by different SDXI nodes/resource devices.

Thus, systems and methods have been described that provide for theconfiguration of an SDXI data plane for an LCS using SDXI node(s) thatare included in the resource device(s) that provide that LCS. Forexample, the LCS SDXI data plane configuration system of the presentdisclosure may include a resource management system coupled to anorchestrator device that is coupled to a plurality of resource devices.The resource management system discovers a first SDXI node in theplurality of resource devices, with the first SDXI node configured toprocess SDXI information and including a first memory subsystem that isconfigured to provide an SDXI memory space. The resource managementsystem also identifies first memory system capabilit(ies) of the firstmemory subsystem included in the first SDXI node and, when the resourcemanagement system subsequently receives an LCS request, it composes anLCS that includes an SDXI data plane provided by the first SDXI nodebased on capabilities requirement(s) identified in the LCS request beingsatisfied by the first memory subsystem capabilit(ies) of the firstmemory subsystem included in the first SDXI node. As such, an LCS may beprovided an SDXI data plane made up of one or more memory subsystem, andin many cases may be provided an SDXI data plane made up of differentmemory systems and/or different types of memory devices.

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

What is claimed is:
 1. A Logically Composed System (LCS) Smart DataAccelerator Interface (SDXI) data plane configuration system,comprising: a plurality of resource devices; an orchestrator device thatis coupled to the plurality of resource devices; and a resourcemanagement system that is coupled to the orchestrator device and that isconfigured to: discover, in the plurality of resource devices, a firstSmart Data Accelerator Interface (SDXI) node, wherein the first SDXInode is configured to process SDXI information and includes a firstmemory subsystem that is configured to provide an SDXI memory space;identify at least one first memory subsystem capability of the firstmemory subsystem included in the first SDXI node; receive, following thediscovery of the first SDXI node and the identification of the at leastone first memory subsystem capability of the first memory subsystemincluded in the first SDXI node, a Logically Composed System (LCS)request; and compose, based on at least one capabilities requirementidentified in the LCS request being satisfied by the at least one firstmemory subsystem capability of the first memory subsystem included inthe first SDXI node, an LCS that includes an SDXI data plane provided bythe first SDXI node.
 2. The system of claim 1, wherein the resourcemanagement system is configured to: discover, in the plurality ofresource devices, a second SDXI node, wherein the second SDXI node isconfigured to process SDXI information and includes a second memorysubsystem that is configured to provide an SDXI memory space; identifyat least one second memory subsystem capability of the second memorysubsystem included in the second SDXI node; and compose, based on the atleast one capabilities requirement identified in the LCS request beingsatisfied by the at least one second memory subsystem capability of thesecond memory subsystem included in the second SDXI node, the LCS thatincludes the SDXI data plane provided by the first SDXI node and thesecond SDXI node.
 3. The system of claim 2, wherein the first memorysubsystem included in the first SDXI node is included in a first memorysystem, and wherein the second memory subsystem included in the secondSDXI node is included in a second memory system that is different thanthe first memory system.
 4. The system of claim 2, wherein the firstmemory subsystem included in the first SDXI node is provided by a firsttype of memory device, and wherein the second memory subsystem includedin the second SDXI node is provided by a second type of memory devicethat is different than the first type of memory.
 5. The system of claim1, wherein the resource management system is configured to discover thefirst SDXI node in the plurality of resource devices by: receiving, fromthe orchestrator device, an SDXI node notification identifying the firstSDXI node.
 6. The system of claim 1, wherein the resource managementsystem is configured to: configure access capabilities of the LCS to theSDXI data plane.
 7. The system of claim 6, wherein the orchestratordevice is configured to: abstract, based on the access capabilitiesconfigured for the LCS to the SDXI data plane, an SDXI memory space ofthe SDXI data plane provided by the first SDXI node.
 8. An InformationHandling System (IHS), comprising: a processing system; and a memorysystem that is coupled to the processing system and that includesinstructions that, when executed by the processing system, cause theprocessing system to provide a Smart Data Accelerator Interface (SDXI)control plane manager engine that is configured to: discover, in aplurality of resource devices that are coupled to an orchestratordevice, a first SDXI node, wherein the first SDXI node is configured toprocess SDXI information and includes a first memory subsystem that isconfigured to provide an SDXI memory space; identify at least one firstmemory subsystem capability of the first memory subsystem included inthe first SDXI node; receive, following the discovery of the first SDXInode and the identification of the at least one first memory subsystemcapability of the first memory subsystem included in the first SDXInode, a Logically Composed System (LCS) request; and compose, based onat least one capabilities requirement identified in the LCS requestbeing satisfied by the at least one first memory subsystem capability ofthe first memory subsystem included in the first SDXI node, an LCS thatincludes an SDXI data plane provided by the first SDXI node.
 9. The IHSof claim 8, wherein the SDXI control plane manager engine is configuredto: discover, in the plurality of resource devices, a second SDXI node,wherein the second SDXI node is configured to process SDXI informationand includes a second memory subsystem that is configured to provide anSDXI memory space; identify at least one second memory subsystemcapability of the second memory subsystem included in the second SDXInode; and compose, based on the at least one capabilities requirementidentified in the LCS request being satisfied by the at least one secondmemory subsystem capability of the second memory subsystem included inthe second SDXI node, the LCS that includes the SDXI data plane providedby the first SDXI node and the second SDXI node.
 10. The IHS of claim 9,wherein the first memory subsystem included in the first SDXI node isincluded in a first memory system, and wherein the second memorysubsystem included in the second SDXI node is included in a secondmemory system that is different than the first memory system.
 11. TheIHS of claim 9, wherein the first memory subsystem included in the firstSDXI node is provided by a first type of memory device, and wherein thesecond memory subsystem included in the second SDXI node is provided bya second type of memory device that is different than the first type ofmemory.
 12. The IHS of claim 8, wherein the SDXI control plane managerengine is configured to discover the first SDXI node in the plurality ofresource devices by: receiving, from the orchestrator device, an SDXInode notification identifying the first SDXI node.
 13. The IHS of claim8, wherein the SDXI control plane manager engine is configured to:configure access capabilities of the LCS to the SDXI data plane.
 14. Amethod for configuring a Smart Data Accelerator Interface (SDXI) dataplane for a Logically Composed System (LCS), comprising: discovering, bya resource management system in a plurality of resource devices that arecoupled to an orchestrator device, a first Smart Data AcceleratorInterface (SDXI) node, wherein the first SDXI node is configured toprocess SDXI information and includes a first memory subsystem that isconfigured to provide an SDXI memory space; identifying, by the resourcemanagement system, at least one first memory subsystem capability of thefirst memory subsystem included in the first SDXI node; receiving, bythe resource management system following the discovery of the first SDXInode and the identification of the at least one first memory subsystemcapability of the first memory subsystem included in the first SDXInode, a Logically Composed System (LCS) request; and composing, by theresource management system based on at least one capabilitiesrequirement identified in the LCS request being satisfied by the atleast one first memory subsystem capability of the first memorysubsystem included in the first SDXI node, an LCS that includes an SDXIdata plane provided by the first SDXI node.
 15. The method of claim 14,further comprising: discovering, by the resource management system inthe plurality of resource devices, a second SDXI node, wherein thesecond SDXI node is configured to process SDXI information and includesa second memory subsystem that is configured to provide an SDXI memoryspace; identifying, by the resource management system, at least onesecond memory subsystem capability of the second memory subsystemincluded in the second SDXI node; and composing, by the resourcemanagement system based on the at least one capabilities requirementidentified in the LCS request being satisfied by the at least one secondmemory subsystem capability of the second memory subsystem included inthe second SDXI node, the LCS that includes the SDXI data plane providedby the first SDXI node and the second SDXI node.
 16. The method of claim15, wherein the first memory subsystem included in the first SDXI nodeis included in a first memory system, and wherein the second memorysubsystem included in the second SDXI node is included in a secondmemory system that is different than the first memory system.
 17. Themethod of claim 15, wherein the first memory subsystem included in thefirst SDXI node is provided by a first type of memory device, andwherein the second memory subsystem included in the second SDXI node isprovided by a second type of memory device that is different than thefirst type of memory.
 18. The method of claim 14, wherein discoveringthe first SDXI node in the plurality of resource devices includes:receiving, by the resource management system from the orchestratordevice, an SDXI node notification identifying the first SDXI node. 19.The method of claim 14, further comprising: configuring, by the resourcemanagement system, access capabilities of the LCS to the SDXI dataplane.
 20. The method of claim 19, further comprising: abstracting, bythe orchestrator device based on the access capabilities configured forthe LCS to the SDXI data plane, an SDXI memory space of the SDXI dataplane provided by the first SDXI node.